Scripts for regenerating client #38
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update local copy of spec from [`TileDB-Server//openapi/v1to3/src/openapi-v1.yaml`](https://github.com/TileDB-Inc/TileDB-Server/blob/main/openapi/v1to3/src/openapi-v1.yaml): ```bash gh api \ -H "Accept: application/vnd.github.raw" \ /repos/TileDB-Inc/TileDB-Server/contents/openapi/v1to3/src/openapi-v1.yaml \ > openapi-v1.yaml ```
st4tdb
approved these changes
May 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a parallel-construction of #37, including:
regen.sh: regenerates the client, applies "custom code" changes (see the commit pointed to by branchpatch), commits to Git[email protected](matching the previous version, and undoing some unnecessary diffs from update v1 endpoints to use carrara #37)DEVELOP.mddocuments how to updateopenapi-v1.yaml, and runregen.sh.See here for a direct comparison of this branch vs. master: master...rw/37
Total diff vs. master is significantly reduced; before (#37):
After (this PR):